Configuring WebLogic

To configure WebLogic use the WebLogic Administration Console. By default the port number is 7001 and /console is the context root. Example: http://hostname:7001/console

Note: When selecting a menu option in the WebLogic Administrative Console, the names may differ depending on whether WebLogic is used in development mode or production mode.

Create a Machine

  1. Select Edit Tree > Environment > Machines > New.

  2. Enter the name for the machine.

  3. If the OS is not UNIX, select Other from the Machine OS drop-down list.

  4. Click Create.

  5. Click on Cart icon on top right corner .

  6. Click Commit Changes.

Create and Configure OIPA Server

Important: OIPA and the Web Application Utility can exist on the same WebLogic server if necessary.

Create the AdminConsole Server

  1. Select Edit Tree > Environment > Servers.

  2. Click New.

  3. Enter AdminConsole for the name of the server and Click on CREATE button.

  4. Set the listener port to a port that is not used by any other application.

  5. Select previously created Machine from the Machine dropdown

  6. Click Save.

  7. Commit the changes by Clicking on Cart icon.

Configure the Admin Console Server

  1. Select Edit Tree > Environment>Servers.

  2. Select the Admin Console server that was created.

  3. Select the Advanced > Node manager tab.

  4. Specify the class path. The path names will vary depending on the configuration.

  5. Save and Commit the changes.

C:/Oracle/Middleware/Oracle_Home/wlserver/server/lib/weblogic.jar; folderpath/libs//commons-logging-1.2-9f99a00.jar;folderpath/conf/

Create Data Sources - Oracle

Create the Data Source for ADMINCONSOLEDS

  1. Select Edit Tree > Services> Data Sources.

  2. Click on NEW button to create data source.

    1. Name : This name can be anything, but has to be unique for the entire WebLogic server. If you have more than one OIPA instance on the server, then each instance should have a unique name.

    2. JNDI Names :

    3. ADMINCONSOLEDS. This name cannot be anything other than ADMINCONSOLEDS.

    4. Targets : Select AdminConsole from Available list and add to Chosen list

    5. Data Source Type: Generic Data Source

    6. Database type : Oracle

    7. Database driver : Oracle Driver (Thin XA) for Service Connections; Version:Any

    8. Enter Database Name.

    9. Enter the Host Name of the database server.

    10. Enter the Port number of the database server.

    11. Enter the Database user name. This can be obtained from the database administrator who installed the databases.

    12. Enter both password entries. This can be obtained from the database administrator who installed the databases.

    13. Click on Create.

    14. Go to Connectionpool and Click on TestConfiguration.

    15. If the connection is successful, Success message will be displayed.

    16. Save and Commit changes.

ac-oipa-jmxconnection-content.xml

This ac-oipa-jmxconnection-content.xml file will have the ports to listen to Cycle/OIPA/Service Layer web servers. Based on count of Cycle/OIPA/Service Layer web managed servers , those many nodes should be created. port of this node should match with port that given in the Cycle/OIPA/Service Layer web arguments.

Cycle/OIPA/Service Layer Web Server changes :

The following arguments should be added in arguments of Cycle/OIPA/Service Layer web each managed servers:

-Dcom.sun.management.jmxremote.port=5555
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
- Dcom.sun.management.jmxremote.autodiscovery=true
-Djavax.management.builder.initial=weblogic.management.jmx.mbeanserver.WLSMBeanServerBuilder
-Dweblogic.oif.serialFilter=java.rmi.server.*
-Dcom.sun.management.jmxremote.rmi.port=9999

 

Add below JVM arguements to ADMINCONSOLE

-Dweblogic.oif.serialFilter=java.rmi.server.*

Ensure below property is configured in respective *.properties file of OIPA/CYCLE/SERVICE LAYER applications for JMX events to publish on Admin Console.

jmx.notification.entities=cycle,activity,activityprofiling,outboundeventpush,serviceauditlogging

Ensure the following property is configured in respective *.properties file of OIPA/CYCLE/SERVICE LAYER applications for JMX events to publish on Admin Console:

jmx.notification.entities=cycle,activity,activityprofiling,outboundeventpush,serviceauditlogging

Note: The 5577 port can be anything which is not used by any other application in the server. Make sure this is open and available port. This port and the port in ac-oipa-jmxconnection-content.xml file should match.